Blog

Brad Wood

July 05, 2013

Spread the word


Share your thoughts

If you're using external Jar files in your project, you may be loading them at run time with Mark Mandel's JavaLoader project.  (CF10 allows for dynamic loading of Jar files, but for people still on CF8, or 9, JavaLoader is the defacto method)
If you're manually creating and using the JavaLoader CFC, please remember that WireBox has a dedicated "JavaLoader" namespace in its mapping DSL to handle this for you using ColdBox's JavaLoader Plugin.  Here all you have to do:

Put a javaloader_libpath setting in your config file that tells ColdBox where the your Jars are:

ColdBox.cfc
// custom settings
settings = {
    javaloader_libpath = "/includes/jars/"
};

If you have more than one Jar directory, simply pass in a comma-delimited list, OR an array of paths.  Your choice.

Now you can inject that class into your components by using the "javaloader" namespace and following it by the Java classpath:

component {
    property name="UASparser" inject="javaLoader:cz.mallat.uasparser.UASparser";
}

That will inject the Java Class definition (which is fine for static classes).  If you need an instance, you'll want to call the init() method to actually instantiate it.

function onDIComplete() {
    oUASparser = UASparser.init(ExpandPath("/includes/uas.ini"));
}

That's not the only way-- this one-liner accomplishes the same thing:

oUASparser = getModel(dsl="javaloader:cz.mallat.uasparser.UASparser").init(ExpandPath("/includes/uas.ini"));

More info here: http://wiki.coldbox.org/wiki/Plugins:JavaLoader.cfm
And here: http://wiki.coldbox.org/wiki/WireBox.cfm#ColdBox_Namespace

Add Your Comment

(2)

Dec 09, 2014 10:39:20 UTC

by Daniel

How to add javaloader_libpath in wirebox standalone..?

Dec 09, 2014 12:11:15 UTC

by Brad Wood

The "javaloader" DSL namespace is only available in WireBox when it is linked to ColdBox. That's because it depends on the JavaLoader Plugin which is part of ColdBox. Note: in ColdBox 4, JavaLoader has been removed from the ColdBox core and is an optional module called cbjavaloader. So you can't use the DSL I showed in this post by default, HOWEVER you can add this into WireBox standalone if you wish. Look at how the cbjavaloader module works-- it registers the "javaloader" DSL on the fly. https://github.com/ColdBox/cbox-javaloader/blob/master/modules/cbjavaloader/ModuleConfig.cfc#L26 You could probably make a standalone version of cbjavaloader that reused the same loader object and registered the DSL. Honestly though, i would save my time and just start using ColdBox :) Using JavaLoader in ColdBox 4 is as simple as this: CommandBox> install cbjavaloader Done!

Recent Entries

A Year in Review - BoxLang 2024 Recap!

A Year in Review - BoxLang 2024 Recap!

BoxLang has come a long way since its beta release, and we're thrilled to share the incredible progress made so far. From its initial launch to the upcoming stable version, BoxLang has been evolving with new features, tools, and a growing ecosystem, all aimed at empowering modern developers.In this recap, we’ll highlight the milestones and advancements that have shaped BoxLang’s journey to this point. Let’s take a look at what we’ve achieved and what’s coming next!

Maria Jose Herrera
Maria Jose Herrera
January 03, 2025
Partner with BoxLang and Ortus at Into the Box 2025: Empowering the Future of Modern Software Development!

Partner with BoxLang and Ortus at Into the Box 2025: Empowering the Future of Modern Software Development!

At Ortus Solutions, we’ve always been at the forefront of innovation in the ColdFusion ecosystem. From pioneering modern ColdFusion practices to developing cutting-edge tools and frameworks, we’ve been passionate to help and sup[port the community into shaping the future of web development.That’s why we decided to build BoxLang, our new JVM programming language that not only builds on the strengths of ColdFusion but takes modern software development to the next level.

Maria Jose Herrera
Maria Jose Herrera
December 23, 2024